Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add CPPF DQM modules #38564

Merged
merged 1 commit into from
Jul 28, 2022
Merged

Add CPPF DQM modules #38564

merged 1 commit into from
Jul 28, 2022

Conversation

zhangcg123
Copy link
Contributor

@zhangcg123 zhangcg123 commented Jun 30, 2022

PR description:

Add CPPF online DQM modules L1TdeStage2CPPF and L1TStage2CPPF.
By comparing the CPPF emulator and unpacker outputs and putting some comparison histograms on the CMS online DQM GUI, shifters can monitor the status of the CPPF hardware.

https://twiki.cern.ch/twiki/bin/viewauth/CMS/CPPFDQMDevelopment
https://indico.cern.ch/event/1096936/contributions/4614848/attachments/2347544/4003548/Ram_CPPFUpdate_20211117.pdf

PR validation:

cmsRun DQM/Integration/python/clients/l1tstage2emulator_dqm_sourceclient-live_cfg.py unitTest=True

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

The PR will have to be backported to 10_4_X

@cmsbuild
Copy link
Contributor

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38564/30811

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@cmsbuild
Copy link
Contributor

+code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38564/30812

@cmsbuild
Copy link
Contributor

A new Pull Request was created by @zhangcg123 for master.

It involves the following packages:

  • DQM/L1TMonitor (dqm)
  • EventFilter/RPCRawToDigi (reconstruction)
  • L1Trigger/Configuration (l1)
  • L1Trigger/L1TMuonCPPF (l1)

@epalencia, @emanueleusai, @ahmad3213, @cmsbuild, @rekovic, @jfernan2, @clacaputo, @jpata, @pmandrik, @micsucmed, @cecilecaillol, @rvenditti can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @missirol, @dinyar, @thomreis, @eyigitba this is something you requested to watch as well.
@perrotta, @dpiparo, @qliphy you are the release manager for this.

cms-bot commands are listed here

@qliphy
Copy link
Contributor

qliphy commented Jul 1, 2022

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Jul 1, 2022

+1

Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-daadf4/25926/summary.html
COMMIT: ba76379
CMSSW: CMSSW_12_5_X_2022-06-30-2300/el8_amd64_gcc10
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/38564/25926/install.sh to create a dev area with all the needed externals and cmssw changes.

Comparison Summary

Summary:

  • No significant changes to the logs found
  • Reco comparison results: 5 differences found in the comparisons
  • DQMHistoTests: Total files compared: 50
  • DQMHistoTests: Total histograms compared: 3654771
  • DQMHistoTests: Total failures: 8
  • DQMHistoTests: Total nulls: 0
  • DQMHistoTests: Total successes: 3654741
  • DQMHistoTests: Total skipped: 22
  • DQMHistoTests: Total Missing objects: 0
  • DQMHistoSizes: Histogram memory added: 2092.8200000000006 KiB( 49 files compared)
  • DQMHistoSizes: changed ( 10024.0,... ): 102.008 KiB L1TEMU/L1TdeStage2CPPF
  • DQMHistoSizes: changed ( 10024.0,... ): 2.633 KiB L1T/L1TStage2CPPF
  • Checked 208 log files, 45 edm output root files, 50 DQM output files
  • TriggerResults: no differences found

@emanueleusai
Copy link
Member

+1

@zhangcg123
Copy link
Contributor Author

@vukasinmilosevic

@zhangcg123
Copy link
Contributor Author

Hi @cecilecaillol, @epalencia, is this ok to go in

@cecilecaillol
Copy link
Contributor

@zhangcg123 Can you please replace the couts with edmLogWarning/Error/... (https://twiki.cern.ch/twiki/bin/view/CMSPublic/SWGuideMessageLogger) ?

@clacaputo
Copy link
Contributor

+reconstruction

  • re-sign after rebase

@perrotta
Copy link
Contributor

@zhangcg123 if I compare with the version before your latest squash I get the following diff in DQM/L1TMonitor/python/L1TStage2Emulator_cff.py:

diff DQM/L1TMonitor/python/L1TStage2Emulator_cff.py $APREL\DQM/L1TMonitor/python/L1TStage2Emulator_cff.py
71,82d70
< from Configuration.Eras.Modifier_run3_common_cff import run3_common
< run3_common.toModify( valCscStage2Digis,
<                       keepShowers = True,
<                       commonParam = dict(run3 = True,
<                                          runCCLUT_OTMB = True,
<                                          runPhase2 = True,
<                                          runME11Up = True,
<                                          runME21Up = True,
<                                          runME31Up = True,
<                                          runME41Up = True)
< )
< 
84c72
< run3_GEM.toModify( valCscStage2Digis, GEMPadDigiClusterProducer = "valMuonGEMPadDigiClusters" , commonParam = dict(runME11ILT = True) )
---
> run3_GEM.toModify( valCscStage2Digis, GEMPadDigiClusterProducer = "valMuonGEMPadDigiClusters" )
103,104d90
< run3_GEM.toModify( valEmtfStage2Digis, UseRun3CCLUT_OTMB = cms.bool(True), Era = cms.string('Run3_2021'))
< 

Could you please check?

@zhangcg123
Copy link
Contributor Author

zhangcg123 commented Jul 27, 2022

@zhangcg123 if I compare with the version before your latest squash I get the following diff in DQM/L1TMonitor/python/L1TStage2Emulator_cff.py:

diff DQM/L1TMonitor/python/L1TStage2Emulator_cff.py $APREL\DQM/L1TMonitor/python/L1TStage2Emulator_cff.py
71,82d70
< from Configuration.Eras.Modifier_run3_common_cff import run3_common
< run3_common.toModify( valCscStage2Digis,
<                       keepShowers = True,
<                       commonParam = dict(run3 = True,
<                                          runCCLUT_OTMB = True,
<                                          runPhase2 = True,
<                                          runME11Up = True,
<                                          runME21Up = True,
<                                          runME31Up = True,
<                                          runME41Up = True)
< )
< 
84c72
< run3_GEM.toModify( valCscStage2Digis, GEMPadDigiClusterProducer = "valMuonGEMPadDigiClusters" , commonParam = dict(runME11ILT = True) )
---
> run3_GEM.toModify( valCscStage2Digis, GEMPadDigiClusterProducer = "valMuonGEMPadDigiClusters" )
103,104d90
< run3_GEM.toModify( valEmtfStage2Digis, UseRun3CCLUT_OTMB = cms.bool(True), Era = cms.string('Run3_2021'))
< 

Could you please check?

Hi @perrotta

The new squash was rebased on the top of the newest merged commits at that time. The diff you mentioned is here.

67f988c#diff-958876a581b9e879b842bdfcb4371f7bef929312c19e0d17a8e5c55484708c71

Thanks

@perrotta
Copy link
Contributor

Thank you @zhangcg123 : then you confirm that the update 67f988c#diff-958876a581b9e879b842bdfcb4371f7bef929312c19e0d17a8e5c55484708c71 that is in this PR was already there in the previous one?
If you can please confirm so, this one can be merged as it is

@cecilecaillol
Copy link
Contributor

+l1

@zhangcg123
Copy link
Contributor Author

Hi @perrotta

I think these changes is not from our side. When we created this PR and now there are couple of PR which is merged.

So, the change that you mention is not from our side. It is from the other PR.

If you check all the files that we changed here:

https://github.com/cms-sw/cmssw/pull/38564/files

This link does not show any additional line/file.

Let me know if I did not get your message.

@perrotta
Copy link
Contributor

perrotta commented Jul 27, 2022

@perrotta , I have to say no, the update was not there before the PR was rebased. As you can see the update was merged into the master 8 days ago. When I was asked to squash my commits into one, I rebased this PR on the top of the newest master(the update had been merged). So, the update was included in this PR. It looks like I should not include the update into this PR? If so, sorry for that. and what I should do? Many thanks.

the update#67f988c#diff-958876a581b9e879b842bdfcb4371f7bef929312c19e0d17a8e5c55484708c71

Ah, ok, now I understand. You rebased on top of an older IB than the one in which #38373 was merged
github does not complain about possible conflicts, and this should be one of the cases in which git is smart enough to keep the updates separated, even if they are only a couple of lines far away each other.
We can have a look at that particular file, but I imagine everything will be smooth.

The squeeze was correct, then. And as soon as @cms-sw/dqm-l2 signs, this PR can get merged

@zhangcg123
Copy link
Contributor Author

@perrotta , we are also getting confused. Thanks for your explanation.

@emanueleusai
Copy link
Member

+1

@cmsbuild
Copy link
Contributor

This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2)

@perrotta
Copy link
Contributor

+1

@cmsbuild cmsbuild merged commit 9fb18d7 into cms-sw:master Jul 28, 2022
@qliphy
Copy link
Contributor

qliphy commented Jul 31, 2022

@zhangcg123 There is a reval error appearing after merging this PR, please have a look and fix soon:

https://cmssdt.cern.ch/SDT/cgi-bin/logreader/el8_amd64_gcc10/CMSSW_12_5_X_2022-07-30-1100/pyRelValMatrixLogs/run/136.8561_RunZeroBias_hBStarTk+RunZeroBias_hBStarTk+HLTDR2_2018_hBStar+RECODR2_2018reHLT_Offline_hBStar+HARVEST2018_hBStar/step3_RunZeroBias_hBStarTk+RunZeroBias_hBStarTk+HLTDR2_2018_hBStar+RECODR2_2018reHLT_Offline_hBStar+HARVEST2018_hBStar.log#/1072-1072

An exception of category 'OutOfRange' occurred while
[0] Processing Event run: 314890 lumi: 591 event: 497522872 stream: 0
[1] Running path 'dqmoffline_step'
[2] Prefetching for module L1TdeStage2CPPF/'l1tdeStage2Cppf'
[3] Calling method for module RPCAMCRawToDigi/'rpcCPPFRawToDigi'
Exception Message:
Out-of-range input for RPCAMCLink::bf_set, position 0: 113
----- End Fatal Exception -------------------------------------------------

@qliphy
Copy link
Contributor

qliphy commented Aug 1, 2022

@zhangcg123 In case you don't know, you can reproduce the error with
runTheMatrix.py -l 136.8561 --job-reports -t 4 --ibeos

The test with CMSSW_12_5_X_2022-07-27-2300 (before your PR merged) is fine,
while not with CMSSW_12_5_X_2022-07-31-0000

@zhangcg123
Copy link
Contributor Author

@qliphy Many thanks for your instruction, I will try to fix the problem as soon as I can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants